Skip to content

Conversation

@elastic-renovate-prod
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
tj-actions/changed-files action patch v46.0.1 -> v46.0.5

Release Notes

tj-actions/changed-files (tj-actions/changed-files)

v46.0.5

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.5

v46.0.4

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.4

v46.0.3

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.3

v46.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: tj-actions/changed-files@v46...v46.0.2


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@shashank-elastic shashank-elastic added the enhancement New feature or request label Oct 28, 2025
@github-actions
Copy link
Contributor

Enhancement - Guidelines

These guidelines serve as a reminder set of considerations when addressing adding a feature to the code.

Documentation and Context

  • Describe the feature enhancement in detail (alternative solutions, description of the solution, etc.) if not already documented in an issue.
  • Include additional context or screenshots.
  • Ensure the enhancement includes necessary updates to the documentation and versioning.

Code Standards and Practices

  • Code follows established design patterns within the repo and avoids duplication.
  • Ensure that the code is modular and reusable where applicable.

Testing

  • New unit tests have been added to cover the enhancement.
  • Existing unit tests have been updated to reflect the changes.
  • Provide evidence of testing and validating the enhancement (e.g., test logs, screenshots).
  • Validate that any rules affected by the enhancement are correctly updated.
  • Ensure that performance is not negatively impacted by the changes.
  • Verify that any release artifacts are properly generated and tested.
  • Conducted system testing, including fleet, import, and create APIs (e.g., run make test-cli, make test-remote-cli, make test-hunting-cli)

Additional Checks

  • Verify that the enhancement works across all relevant environments (e.g., different OS versions).
  • Confirm that the proper version label is applied to the PR patch, minor, major.

Copy link
Contributor

@shashank-elastic shashank-elastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Used only in .github/workflows/kibana-mitre-update.yml. Thats run once a year and the release change list upgrades dependant packages and does not affect any functionality.
Safe to merge

Copy link
Contributor

@eric-forte-elastic eric-forte-elastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Manual review, looks good to me! 👍

Related Context: #4542

@shashank-elastic shashank-elastic merged commit f52aedf into main Oct 28, 2025
16 checks passed
@shashank-elastic shashank-elastic deleted the renovate/tj-actions-changed-files-46.x branch October 28, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants